Communication interface for non-communication applications

ABSTRACT

Software applications are enabled with multimodal communication capabilities and features associated with enhanced communication systems through a communication application programming interface (API). Applications for document processing, scheduling, audio/video data processing, and/or business operations can exchange communication system data and parameters bi-directionally with components of an enhanced communication system, initiate communication sessions through the application&#39;s user interface, and preserve post-communication updates.

BACKGROUND

Modern communication systems such as unified communications (UC) systemscombine various modes of communication (e.g. instant messaging, voicecalls, video communications, etc.) and provide ancillary services likepresence, recording, interactive contact lists, etc. With the evereasier to establish single or multimodal conversations and sharingcapabilities, physical distances between co-workers, partners, andcolleagues are eliminated through virtual connections.

Another set of tools that makes life easier and increases efficiencyincludes a wide variety of applications that enables users tocreate/edit/share word processing documents, spreadsheets, calendars,presentations, analyses, reports, audio files, video files, andcomparable ones. The data (e.g., documents) created by such applicationsare typically part of the context of discussions and exchanges betweenusers of enhanced communication services. To include such contextualdata in communication sessions, however, users typically have toactivate a communication application, a relevant application or datasharing component and then exchange the information. Moreover, a numberof potential capabilities of the communication applications or otherapplications are not exploited since communication applications andother applications are typically unrelated programs.

SUMMARY

This summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This summary is not intended to exclusively identify keyfeatures or essential features of the claimed subject matter, nor is itintended as an aid in determining the scope of the claimed subjectmatter.

Embodiments are directed to enabling software applications withmultimodal communication capabilities and features associated withenhanced communication systems. According to some embodiments, acommunication application programming interface (API) may be providedfor applications such as document processing, scheduling, audio/videodata processing, business applications, and comparable ones such thatcommunication system data and parameters can be bi-directionallyexchanged, communication sessions initiated through an application userinterface, and post-communication updates preserved through theapplication.

These and other features and advantages will be apparent from a readingof the following detailed description and a review of the associateddrawings. It is to be understood that both the foregoing generaldescription and the following detailed description are explanatory anddo not restrict aspects as claimed.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a conceptual diagram illustrating an example networkedcommunication and document use environment, where a communicationinterface for non-communication applications may be implemented;

FIG. 2 illustrates an example implementation of enhanced communicationcapable non-communication application according to some embodiments;

FIG. 3 illustrates an example object model for a communication API to beimplemented in a non-communication application according to embodiments;

FIG. 4 is a networked environment, where a system according toembodiments may be implemented;

FIG. 5 is a block diagram of an example computing operating environment,where embodiments may be implemented; and

FIG. 6 illustrates a logic flow diagram for a process of providingenhanced communication capabilities in a non-communication applicationaccording to some embodiments.

DETAILED DESCRIPTION

As briefly described above, non-communication software applications maybe enabled with multimodal communication capabilities and featuresassociated with enhanced communication systems through a communicationapplication programming interface (API). Applications for documentprocessing, scheduling, audio/video data processing, and/or businessoperations can exchange communication system data and parametersbi-directionally with components of an enhanced communication system,initiate communication sessions through the application's userinterface, and preserve post-communication updates. In the followingdetailed description, references are made to the accompanying drawingsthat form a part hereof, and in which are shown by way of illustrationsspecific embodiments or examples. These aspects may be combined, otheraspects may be utilized, and structural changes may be made withoutdeparting from the spirit or scope of the present disclosure. Thefollowing detailed description is therefore not to be taken in alimiting sense, and the scope of the present invention is defined by theappended claims and their equivalents.

While the embodiments will be described in the general context ofprogram modules that execute in conjunction with an application programthat runs on an operating system on a computing device, those skilled inthe art will recognize that aspects may also be implemented incombination with other program modules.

Generally, program modules include routines, programs, components, datastructures, and other types of structures that perform particular tasksor implement particular abstract data types. Moreover, those skilled inthe art will appreciate that embodiments may be practiced with othercomputer system configurations, including hand-held devices,multiprocessor systems, microprocessor-based or programmable consumerelectronics, minicomputers, mainframe computers, and comparablecomputing devices. Embodiments may also be practiced in distributedcomputing environments where tasks are performed by remote processingdevices that are linked through a communications network. In adistributed computing environment, program modules may be located inboth local and remote memory storage devices.

Embodiments may be implemented as a computer-implemented process(method), a computing system, or as an article of manufacture, such as acomputer program product or computer readable media. The computerprogram product may be a computer storage medium readable by a computersystem and encoding a computer program that comprises instructions forcausing a computer or computing system to perform example process(es).The computer-readable storage medium can for example be implemented viaone or more of a volatile computer memory, a non-volatile memory, a harddrive, a flash drive, a floppy disk, or a compact disk, and comparablemedia.

Throughout this specification, the term “platform” may be a combinationof software and hardware components for managing enhanced communicationsystems. Examples of platforms include, but are not limited to, a hostedservice executed over a plurality of servers, an application executed ona single server, and comparable systems. The term “server” generallyrefers to a computing device executing one or more software programstypically in a networked environment. However, a server may also beimplemented as a virtual server (software programs) executed on one ormore computing devices viewed as a server on the network. More detail onthese technologies and example operations is provided below.

FIG. 1 is a conceptual diagram illustrating an example networkedcommunication and document use environment, where a communicationinterface for non-communication applications may be implemented. Anenhanced communication system can facilitate multimodal communicationsbetween users including sharing of various forms of data such asdocuments.

A unified communication (UC) system is an example of enhancedcommunication systems with a wide range of capabilities and servicesthat can be provided to subscribers. A unified communication system is areal-time communications system facilitating email exchange, instantmessaging, presence, audio-video conferencing, web conferencing, andsimilar functionalities.

In a UC system such as the one shown in diagram 100, users maycommunicate via a variety of end devices 114 and 120, which are clientdevices of the UC system. Each client device may be capable of executingone or more communication applications for voice communication, videocommunication, instant messaging, application sharing, data sharing, andthe like. In addition to their advanced functionality, the end devicesmay also facilitate traditional phone calls through an externalconnection such as through Private Branch Exchange (PBX) to a PublicSwitched Telephone Network (PSTN) or cellular communications through acellular network.

The communication system shown in diagram 100 may include a number ofservers performing different tasks. For example, communication server104 may manage conversations between users (112, 118) over one or morenetworks 102. Separately from the communication system, users 112 and118 may have locally installed applications 116 and 122 for a variety oftasks such as document processing, analysis, calendaring, scheduling,audio or video data processing, graphic processing, and similar ones. Insome cases, application 116 and 122 may be client applications of ahosted service executed by server 106. In such scenarios, data (e.g.,documents, images, audio/video files, etc.) may be shared between usersand provided to the individual users from server 106 (e.g. documents108, 110).

In a system according to embodiments, applications 116, 122 may beenabled with multimodal communication capabilities and featuresassociated with the enhanced communication systems through acommunication API. Applications 116, 122 may exchange communicationsystem data and parameters (e.g., rich presence information)bi-directionally with components of the enhanced communication system,facilitate communication sessions in one or more modalities (e.g., starta conversation in one or more modalities, join a conference, sharedata/applications) through the application's user interface, andpreserve post-communication updates (e.g., changes to shareddocuments/data, conversation history, etc.).

While the example system in FIG. 1 has been described with specificcomponents such as communication servers, application servers, andsimilar devices, embodiments are not limited to these components orsystem configurations and can be implemented with other systemconfiguration employing fewer or additional components. A communicationinterface for non-communication applications may be implemented in adistributed manner among the components of the system depending oncomponent capabilities and system configuration. Furthermore,embodiments are not limited to unified communication systems. Theapproaches discussed here may be applied to any multimodal communicationsystem using the principles described herein.

FIG. 2 illustrates an example implementation of enhanced communicationcapable non-communication application according to some embodiments.While integration with enhanced communication systems may be implementedwith any application, a presentation application is displayed as examplein diagram 200.

Presentation application user interface 202 may display a presentation206 and provide controls 204 for editing various aspects of thepresentation 206. The presentation application may be locally installedor a hosted application accessed through a thin client (e.g., abrowser). Thus, presentation application user interface 202 may be theuser interface of the locally installed application or a web pagecustomized for providing the features of a hosted presentationapplication. According to some embodiments, an embedded communicationuser interface 208 may be provided through a communication API.Communication user interface 208 may also be a “docked” user interface(i.e., a separate user interface attached to the presentationapplication user interface 202).

The presentation application may communicate with servers 212 andclients 214 of communication system 210 facilitating single ormultimodal communications and receiving data associated withcommunication system features. For example, contact informationassociated with an organization may be retrieved by the presentationapplication to enable a user initiate communication sessions with otherusers in the organization. The same data may also be utilized forinherent functions of the presentation application such as creating anorganization chart, etc.

According to an example scenario, a user may initiate a multimodalcommunication session involving audio communications, videocommunications, and application sharing through the communication userinterface 208. Upon establishment of the communication session, new userinterfaces 216, 218, and 220 may be provided for the respectivemodalities either as separate user interfaces or in an embedded format.For example, presentation 206 may be displayed in application sharinguser interface 220 for collaboration during the communication session.Changes may be made to the presentation during the communicationsession. The updated presentation 222 may be saved and/or displayed inthe presentation application user interface 202 upon completion of thecommunication session. Additional data such as conversation history andany other information created or modified during the communicationsession may also be preserved by the presentation application.

FIG. 3 illustrates an example object model for a communication API to beimplemented in a non-communication application. According to someembodiments, a rich API may be exposed to non-communication applicationsallowing them to integrate with enhanced communication systems to getrich presence information, start conversation, join conference,start/communicate with participants with different modalities, andperform other communication related tasks.

As diagram 300 shows, communication client 302 is a root entry point forthe application. Contact manager 306, conversation manager 316, anddevice manager 336 are management objects that can be accessed throughthe root object and manage other object groups. Contact manager 306 maymanage individual contact objects 314, contact group objects 312, andrelated classes, including search objects 308 and subscription objects(for presence) 310. Contact and group information may be obtainedthrough instances of those classes.

Conversation manager object 316 manages conversations 318. Theapplication using the API may create conversations 318, start or acceptdifferent modalities 322, add or remove participants 320, and startaudio and/or video by accessing the instances of audio channel 324 andvideo channel 326 classes under conversation manager 316. Device manager336 manages registered audio and video devices 338 and 340 through whichmultimodal communications may be facilitated.

From the root object communication client 302, a self class 328 may beexposed to manage the permissions 330 granted for other contacts toaccess a user's published information. Users may also be enabled topublish their contact information (334) to the communication system oredit their phones 332 under the self class 328. The communication APImay also provide extensibility classes 342, for callers to make simpleAPI calls to start conversations (automation 344), for docking/undockinga conversation window 346, and for registering application packages 348that can be used for extensibility.

The object model for the communication API illustrated in diagram 300 isan example one, and does not constitute a limit on embodiments. An APIaccording to embodiments may include additional or fewer objects. Forexample, user's computing device capabilities (processing power,available memory, etc.), application's capabilities, networkcapabilities, and similar ones may be managed as objects by the API.

FIG. 4 is an example networked environment, where embodiments may beimplemented. Enabling non-communication applications with communicationcapabilities through a communication API may be implemented via softwareexecuted over one or more servers 414 or a single server (e.g. webserver) 416 such as a hosted service. The platform may communicate withclient applications on individual computing devices such as a smartphone 413, a laptop computer 412, or desktop computer 411 ('clientdevices') through network(s) 410 providing communication and otherservices.

As discussed above, multimodal communication capabilities and featuresassociated with enhanced communication systems may be integrated intoapplications for document processing, scheduling, audio/video dataprocessing, and/or business operations enabling them to exchangecommunication system data and parameters bi-directionally withcomponents of an enhanced communication system, initiate communicationsessions through the application's user interface, and preservepost-communication updates.

Client devices 411-413 may enable access to communication applicationsexecuted on remote server(s) (e.g. one of servers 414) as discussedpreviously. The server(s) may retrieve or store relevant data from/todata store(s) 419 directly or through database server 418.

Network(s) 410 may comprise any topology of servers, clients, Internetservice providers, and communication media. A system according toembodiments may have a static or dynamic topology. Network(s) 410 mayinclude secure networks such as an enterprise network, an unsecurenetwork such as a wireless open network, or the Internet. Network(s) 410may also coordinate communication over other networks such as PublicSwitched Telephone Network (PSTN) or cellular networks. Furthermore,network(s) 410 may include short range wireless networks such asBluetooth or similar ones. Network(s) 410 provide communication betweenthe nodes described herein. By way of example, and not limitation,network(s) 410 may include wireless media such as acoustic, RF, infraredand other wireless media.

Many other configurations of computing devices, applications, datasources, and data distribution systems may be employed to providecommunication capabilities to non-communication applications.Furthermore, the networked environments discussed in FIG. 4 are forillustration purposes only. Embodiments are not limited to the exampleapplications, modules, or processes.

FIG. 5 and the associated discussion are intended to provide a brief,general description of a suitable computing environment in whichembodiments may be implemented. With reference to FIG. 5, a blockdiagram of an example computing operating environment for an applicationaccording to embodiments is illustrated, such as computing device 500.In a basic configuration, computing device 500 may be any computingdevice executing a non-communication application with a capability toconnect to a network and include at least one processing unit 502 andsystem memory 504. Computing device 500 may also include a plurality ofprocessing units that cooperate in executing programs. Depending on theexact configuration and type of computing device, the system memory 504may be volatile (such as RAM), non-volatile (such as ROM, flash memory,etc.) or some combination of the two. System memory 504 typicallyincludes an operating system 505 suitable for controlling the operationof the platform, such as the WINDOWS® operating systems from MICROSOFTCORPORATION of Redmond, Wash. The system memory 504 may also include oneor more software applications such as program modules 506, application522, communication user interface 524, and communication API 526.

Application 522 may be any application that provides a wide variety ofservices such as editing documents, analysis, reporting, calendaring,scheduling, viewing, and so on. Communication API 526 may enableapplication 522 with communication capabilities through an enhancedcommunication system such that data like presence information can beexchanged, communication sessions initiated and facilitated throughcommunication user interface 524, and post-communication updatespreserved at the application 522. This basic configuration isillustrated in FIG. 5 by those components within dashed line 508.

Computing device 500 may have additional features or functionality. Forexample, the computing device 500 may also include additional datastorage devices (removable and/or non-removable) such as, for example,magnetic disks, optical disks, or tape. Such additional storage isillustrated in FIG. 5 by removable storage 509 and non-removable storage510. Computer readable storage media may include volatile andnonvolatile, removable and non-removable media implemented in any methodor technology for storage of information, such as computer readableinstructions, data structures, program modules, or other data. Systemmemory 504, removable storage 509 and non-removable storage 510 are allexamples of computer readable storage media. Computer readable storagemedia includes, but is not limited to, RAM, ROM, EEPROM, flash memory orother memory technology, CD-ROM, digital versatile disks (DVD) or otheroptical storage, magnetic cassettes, magnetic tape, magnetic diskstorage or other magnetic storage devices, or any other medium which canbe used to store the desired information and which can be accessed bycomputing device 500. Any such computer readable storage media may bepart of computing device 500. Computing device 500 may also have inputdevice(s) 512 such as keyboard, mouse, pen, voice input device, touchinput device, and comparable input devices. Output device(s) 514 such asa display, speakers, printer, and other types of output devices may alsobe included. These devices are well known in the art and need not bediscussed at length here.

Computing device 500 may also contain communication connections 516 thatallow the device to communicate with other devices 518, such as over awireless network in a distributed computing environment, a satellitelink, a cellular link, and comparable mechanisms. Other devices 518 mayinclude computer device(s) that execute communication applications,storage servers, and comparable devices. Communication connection(s) 516is one example of communication media. Communication media can includetherein computer readable instructions, data structures, programmodules, and includes any information delivery media. By way of example,and not limitation, communication media includes wired media such as awired network or direct-wired connection, and wireless media such asacoustic, RF, infrared and other wireless media.

Example embodiments also include methods. These methods can beimplemented in any number of ways, including the structures described inthis document. One such way is by machine operations, of devices of thetype described in this document.

Another optional way is for one or more of the individual operations ofthe methods to be performed in conjunction with one or more humanoperators performing some. These human operators need not be co-locatedwith each other, but each can be only with a machine that performs aportion of the program.

FIG. 6 illustrates a logic flow diagram for a process of enhancedcommunication capabilities in a non-communication application accordingto embodiments. Process 600 may be implemented by a computing deviceexecuting an application and having network connectivity.

Process 600 may begin at operation 610, where a rich API is exposed tothe application enabling the application to integrate with enhancedcommunication systems. As discussed previously, a root entry pointobject may be used for a number of manager objects managing differentcapabilities and functionalities associated with enhanced communicationservices. At operation 620, the application may be enabled to retrievedata from the communication system such as presence information, contactinformation, and comparable ones. The data may be used in communicationfunctionality as well as for inherent purposes of the application. Forexample, if the application is a scheduling application, it may use thereceived presence data to set up schedules.

At operation 630, data associated with the application and/or user maybe published to the communication system by the application. Atoperation 640, a request may be received from a user to initiate acommunication session through a communication portion of the applicationuser interface enabled by the communication API. At operation 650, theapplication may facilitate the communication session, enabling exchangeof data associated with the application's inherent functions. Atoperation 660, any updated application data may be preserved by theapplication upon completion of the communication session. For example,if the communication session involves sharing of a presentation andchanges are made during the communication session, the updatedpresentation may be saved by the application.

The operations included in process 600 are for illustration purposes.Enhanced communication capabilities in a non-communication applicationaccording to embodiments may be implemented by similar processes withfewer or additional steps, as well as in different order of operationsusing the principles described herein.

The above specification, examples and data provide a completedescription of the manufacture and use of the composition of theembodiments. Although the subject matter has been described in languagespecific to structural features and/or methodological acts, it is to beunderstood that the subject matter defined in the appended claims is notnecessarily limited to the specific features or acts described above.Rather, the specific features and acts described above are disclosed asexample forms of implementing the claims and embodiments.

What is claimed is:
 1. A method executed at least in part by a computingdevice for enabling non-communication applications with enhancedcommunication capabilities, the method comprising: exposing a richcommunication application programming interface (API) provided by anembedded user interface to a non-communication application, wherein theexposure allows the non-communication application to integrate withenhanced communication systems to achieve rich presence information andperform communication related tasks; receiving communication-relateddata from an enhanced communication system through the API; publishingdata to the enhanced communication system through the API; and enablingfacilitation of multimodal communication sessions employing acommunication user interface integrated to a user interface of thenon-communication application through the API, wherein thenon-communication application data is accessed through a thin client andexchanged bi-directionally with the communication system; uponestablishment of the communication session that includes applicationsharing, activating one of an embedded and the attached user interfacefor facilitating the application sharing.
 2. The method of claim 1,further comprising: upon completion of a communication session,preserving modifications to non-communication application data and-related data at the non-communication application.
 3. The method ofclaim 1, further comprising: employing the receivedcommunication-related data and a plurality of parameters in initiationof a communication session.
 4. The method of claim 1, wherein thecommunication user interface is one of embedded and docked to thenon-communication application user interface.
 5. The method of claim 1,wherein the non-communication application is one of locally installedand hosted.
 6. The method of claim 1, wherein the non-communicationapplication provides functionality associated with at least one from aset of: document processing, spreadsheet processing, presentation,analysis, calendaring, scheduling, audio data processing, video dataprocessing, and graphics processing.
 7. The method of claim 1, whereinthe multimodal communication sessions include at least one from a setof: an audio modality, a video modality, a data sharing modality, anapplication sharing modality, white boarding modality, a text messagingmodality, an email exchange modality, and an online conferencingmodality.
 8. The method of claim 7, wherein the communication-relateddata includes at least one from a set of: contact information, presenceinformation, and modality information.
 9. A computing device executing anon-communication application and capable of connecting to an enhancedcommunication system, the computing device comprising: a memory storinginstructions; a communication server, the communication server managingconversations between users over at least one network; a processorcoupled to the memory, the processor executing the non-communicationapplication and exposing a communication application programminginterface (API) to the non-communication application in conjunction withthe instructions stored in the memory, wherein the communication API isconfigured to enable the non-communication application to: receivecommunication-related data from the enhanced communication system;manage the users computing device capabilities, applicationscapabilities, and network capabilities, including one or more ofprocessing power and available memory; publish data to the enhancedcommunication system; employ the received communication-related data ininitiation of a multimodal communication session; facilitate themultimodal communication session employing a communication userinterface integrated to user interface of the non-communicationapplication; and preserve a conversation history, newly created data,and modified data during the multimodal communication session, whereinthe communication API includes a communication client object as a rootentry point for the non-communication application, a contact manager, aconversation manager, and a device manager.
 10. The computing device ofclaim 9, wherein the contact manager manages at least one from a set of:individual contact objects, contact group objects, search objects, andsubscription objects.
 11. The computing device of claim 9, wherein theconversation manager manages conversation objects that enable thenon-communication application to create conversations, modality objectsthat enable one of starting a modality and accepting-a the modality,participant objects that enable one of addition and removal ofparticipants, an audio channel object for starting and audioconversation, and a video channel object for starting a videoconversation.
 12. The computing device of claim 9, wherein the devicemanager manages registered audio and video devices to facilitatemultimodal communications.
 13. The computing device of claim 9, whereinthe API further includes a self class to manage permissions objectsrepresenting granted permissions for other contacts to access a user'spublished information and a publication object to enable thenon-communication application to publish the users contact informationto the enhanced communication system.
 14. The computing device of claim9, wherein the API further includes one or more extensibility classesthat manage an automation object for enabling a user to startconversations through an API call, a conversation window object toenable docking and undocking of a conversation user interface, and aregistration object for registering application packages to be used forextensibility.
 15. The computing device of claim 9, wherein the APIfurther includes an object representing the computing devices'capabilities, another object representing the non-communicationapplication's capabilities, and a further object representing networkcapabilities.
 16. A computer-readable memory device with instructionsstored thereon for enabling non-communication applications with enhancedcommunication capabilities, the instructions comprising: exposing a richcommunication application programming interface (API) provided by anembedded user interface to a non-communication application, wherein theexposure allows the non-communication application to integrate withenhanced communication systems to achieve rich presence information,start a conversation, join a conference, start and communicate withparticipants with different modalities, and perform communicationrelated tasks; receiving communication-related data from an enhancedcommunication system; publishing data to the enhanced communicationsystem; receiving a request from a user to initiate a multimodalcommunication session through a communication portion of an applicationuser interface enabled by the communication API; employing the receivedcommunication-related data in initiation of a multimodal communicationsession; facilitating the multimodal communication session employing acommunication user interface integrated to a user interface of thenon-communication application; and upon completion of the multimodalcommunication session, preserving a conversation history, newly createdinformation, and modifications to non-communication application data andthe communication-related data at the non-communication application;wherein the instructions comprise: employing the receivedcommunication-related data for at least one inherent function of thenon-communication application.
 17. The computer-readable memory deviceof claim 16, wherein the non-communication application user interface isone of a rich client user interface associated with a locally installedapplication and a browser for accessing a hosted non-communicationapplication.